fix: bump Tempo deps and validate fork schedule compatibility#14481
Closed
0xrusowsky wants to merge 4 commits intofoundry-rs:masterfrom
Closed
fix: bump Tempo deps and validate fork schedule compatibility#144810xrusowsky wants to merge 4 commits intofoundry-rs:masterfrom
0xrusowsky wants to merge 4 commits intofoundry-rs:masterfrom
Conversation
Contributor
Author
|
Superseded by #14485 (re-opened from an upstream branch so the |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
tempoxyz/tempoworkspace deps to8bd4d01d37e3cc324030baacbce2da0862d7735atempo_forkScheduleon configured Tempo RPCs and parses the response withTempoHardforkci-tempobefore the script-based Tempo checksContext
Older Foundry Tempo pins only knew hardforks through
T4. When a node reportsactive: "T5",is_hardfork_active(T3)can silently returnfalse, which causescast keychainto choose the legacy authorize selector on T3+ chains.The new integration test makes that mismatch obvious by failing as soon as a configured Tempo RPC reports a fork name this Foundry pin cannot parse.
Verification
cargo check -p cast -p anvil -p forge --lockedTEMPO_MAINNET_RPC_URL=https://rpc.tempo.xyz TEMPO_TESTNET_RPC_URL=https://rpc.moderato.tempo.xyz cargo test --locked -p cast --test cli tempo_fork_schedule_parses_configured_rpcs -- --exact --nocapture